home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
wildcat
/
vfx401.zip
/
VERIFIX.ZIP
/
VERIFIX.DOC
< prev
next >
Wrap
Text File
|
1992-08-29
|
76KB
|
1,651 lines
V E R I F I X
Call Back Verifier for Wildcat! 3.x+ BBSs
"THE NEW STANDARD IN CALL BACK VERIFICATION"
Version 4.01
(c) 1990, 1991, 1992
By Sophisticated Software
ALL RIGHTS RESERVED
Support System Sophisticated Software BBS
(215)968-4998
FidoNET 1:273/215
EchoNET 50:5215/215
Baud: 38400/19200/9600/2400/1200 V.32Bis/V.42
Copyright (c) 1990-1992 Sophisticated Software All Rights Reserved
────────────────────────────────────────────────────────────────────────────
ACKNOWLEDGMENTS
Beta Testers
We couldn't produce a bug free product without the dedications of
our beta testers. These people have worked very hard to catch
bugs by putting VERIFIX to the grinder. Thanks so much for all
your help! Here is the list of beta testers, please call their
fine BBSs:
Bob McGrath -- Modem Addictus BBS -- (615) 579-5094
Mark Ingenito -- The Cheyenne BBS -- (215) 544-7710
Iben Aperson -- The HOLE in the WALL (206) 445-5444
Brad Ship -- ChowdaNet BBS (401) 331-0907
Victor Montgomery -- The COMAX BBS -- (803) 879-4364
Roger Davis -- (310) 947-3997
Tools Used
The following tools are used in creating and maintaining VERIFIX:
Compiler: Microsoft C/C++ 7.0
Libraries: TCXL graphics library (Mike Smedley), MCOMM
serial I/O library (Mike Dumdei)
Editors: Brief 3.1 (Solution Systems)
Documentation: Microsoft Word for Windows 2.0A
CONTACTING SOPHISTICATED SOFTWARE
You can contact Sophisticated Software at the following
address:
By mail:
Sophisticated Software
P.O. Box 55
Newtown, PA 18940-0055
Electronically:
Support: (215) 968-4998, Newtown, PA, at 1200 to 38400 Baud, 24
hours a day, no parity, 8 data bits, 1 stop bit.
EVALUATION KEY
Verifix requires a special file called a "key" to active its usage
for 45 days. This method enables all features for a predetermined
length of time. This is called an evaluation period. As you can
see the evaluation period is 45 days, in which you must register
the program, or it will cease to run.
Packaging a key file with verifix would not be very efficient. If
you recieved this .zip file 60 days from now, the key would be
expired. There is a much better method though. You must call the
support bbs, and create a key file while online. This ensures the
full 45 days to evaluate. Selecting "[E] download dEmo key" from
────────────────────────────────────────────────────────────────────────────
VERIFIX Call Back Verifier Manual Page -1-
Copyright (c) 1990-1992 Sophisticated Software All Rights Reserved
────────────────────────────────────────────────────────────────────────────
the main menu on the support BBS starts the process. The program
will prompt you for information, then you will be able to download
your demo key file using Zmodem, Ymodem or Xmodem!
Again, the BBS support number is (215) 968-4998
FidoNet 1:273/215
NOTE: for anyone that is a member of fidonet, you can also get a
demo key. This is how it is done. In a netmail message, tell me
your full name, address, phone number (home and bbs) AND your
wildcat registration number. (I NEED ALL INFORMATION AS MENTIONED
OR I CANNOT PROCESS YOUR REQUEST FOR A KEY.) I will process this
information and put the key file on HOLD for you. All you need to
do is poll me the next day and you will get your file.
DISCLAIMER
Sophisticated Software hereby disclaims all warranties relating to
this product, whether expressed or implied, including without
limitation any implied warranties of merchant ability or fitness
for a particular purpose. Sophisticated Software cannot and will
not be liable for any special, incidental, consequential, indirect
or similar damages due to loss of data or any other reason, even
if Sophisticated Software or an authorized Sophisticated Software
agent has been advised of the possibility of such damages. In no
event shall the liability for any damages ever exceed the price
paid for the license to use software, regardless of the form
and/or extent of the claim. The user of this program bears all
risk as to the quality and performance of the software.
SHAREWARE ANNOUNCEMENT
VERIFIX is a fully functional SHAREWARE product. It is NOT free
and it is NOT in the public domain. If, after evaluating the
program for 45 days, you find it to be useful enough to use it on
a regular basis, you are expected to pay for it by registering
with Sophisticated Software. The registration fee is $25.00. The
registered .KEY file shall NOT be distributed. The registered
version will display your BBS name in the opening screen.
To become a registered user after the 45 day demonstration period,
just print the ORDER.FRM included with this ZIP file. After
receiving your check / money order a REGISTERED KEY file will be
posted on the SUPPORT BBS within 24 hours. You will be notified
on your next log in by a message from the author what the name of
the keyfile is and the password needed to download it. The
registered KEY will work with all present and future versions of
VERIFIX. The beauty of being a registered verifix user is that
there is only a one time fee for registration. All future
upgrades are FREE! Each new version of VERIFIX can be downloaded
from the supportsupport BBS or the CATHOUSE BBS (Mustang's HQ
BBS).
INTRODUCTION
Welcome! Thanks for considering VERIFIX to be YOUR call back
────────────────────────────────────────────────────────────────────────────
VERIFIX Call Back Verifier Manual Page -2-
Copyright (c) 1990-1992 Sophisticated Software All Rights Reserved
────────────────────────────────────────────────────────────────────────────
verifier! VERIFIX was created for the Wildcat! 3.x+ System
Operator. Many BBS systems have lots of new users calling every
day. Wouldn't it be nice to see if the user on the other side of
the modem is really who they say they are? Well, now you can with
VERIFIX! This program will automatically call the user back and
"verify" him / her in less then 2 minutes. Once configured,
VERIFIX runs by itself, unattended, and working very hard for you.
VERIFIX will automatically verify new or existing users by a
"hands-off" approach. This will put an end to lengthy voice
calls, and make you sleep better at night knowing that the names
in your Wildcat! database are "real" people. VERIFIX will
automatically upgrade the user to a verified level that you
specify. The goal is to keep the program, configuration, and
operation as simple as possible, while still maintaining complete
flexibility and functionality.
One thing to keep in mind while reading this documentation.
VERIFIX is a door, but it is NOT a game! You won't be winning any
prizes, killing any aliens, or be asking the caller trivia
questions. It can be thought of as a utility door. Because of
this, it is a bit more complicated to set up than your average
door. For instance, there are about 8 lines in a normal door
config file. VERIFIX has about 60 lines written to a structure.
You also need to create another control file in addition to the
.cfg file. The reason for all this is because every area in the
U.S. has a different situation as far as calling back users.
Please don't feel intimidated by all this, it just means that
VERIFIX is super flexible when it comes to YOUR NEEDS. If I could
offer a suggestion now, it would be to READ THE ENTIRE .DOC FILE
before setting it up, or print it out then read it. Once you set
up VERIFIX it runs forever. You only have to edit the config
files if you move, or if the phone company changes something on
you. (adding a new area code etc...)
Mission
Sophisticated Software has accepted the challenge to produce the
BEST call back verifier for wildcat. We will be the undisputed
champion in serving our customers!
Technical Support
You can contact us at the BBS number given above, or by sending a
netmail message through the FidoNet network system. My node
address is 1:273/215.
Before contacting us for technical support, please consult the
documentation or manual first. If you don't find what you need,
you can contact us; please give us 24 hours for a reply.
FEATURES
* Compatible with Wildcat! 3.x+.
* Multiple upgrade levels.
────────────────────────────────────────────────────────────────────────────
VERIFIX Call Back Verifier Manual Page -3-
Copyright (c) 1990-1992 Sophisticated Software All Rights Reserved
────────────────────────────────────────────────────────────────────────────
* Creates a bulletin or hello screen.
* Automatically upgrades the user to the security level of
your choice.
* Will upgrade a long distance user without call back, if SysOp
specifies
* Gives additional on-line time to the new user upon
verification. The SysOp decides how much time to add, if
any.
* Writes log files in any directory you specify.
* Has multi-area code capability. This feature is useful
for people that have more than 1 local area code.
* Collision (incoming call) protection. VERIFIX displays a
friendly message to the incoming caller's screen. This
informs them a verification is in progress, and to try
calling back later..
* Long distance protection. You can determine if long
distance area codes OR long distance prefixes are allowed to
be called.
* Single node AND full multi-node operation in ONE program.
* Has a "local" mode when running from DOS or under Wildcat.
This is useful for testing your display screens.
* SysOp can specify a time range that VERIFIX will NOT call
out to verify users.
* Plays user configurable ANSI music for VERIFIED, FAILED
VERIFIED, or CONNECTED operation. This auditory feedback
enables the SysOp to determine the status of verifix. (i.e.
FOGHORN tune means user failed verification)
* Local or long distance verified users have the option of
downloading your "allfiles" file listing.
* Supports @ color codes and .BBS file extension, just like
Wildcat! You only need 1 file for both ansi and mono screen
displays.
* Written in 100% Microsoft C 7.0. No BRUN modules!
* Supports locked baud rates up to 115,200 baud, Com1, Com2,
Com3, Com4 (ANSI standard addresses).
* Supports NON-STANDARD communication ports. Will read the
Wildcat! .MDM file for modem info.
* Easy to setup configuration file using the enclosed editor
VCONFIG.
────────────────────────────────────────────────────────────────────────────
VERIFIX Call Back Verifier Manual Page -4-
Copyright (c) 1990-1992 Sophisticated Software All Rights Reserved
────────────────────────────────────────────────────────────────────────────
* Re-validation protection, if desired.
* Checks user entered area code and prefix against a SysOp
defined areacode.bad file and prefix.bad file for
protection.
* Creates log files to show exactly what the user has done.
Also writes to the Wildcat! ACTIVITY.### log of that node.
* SysOp can create customized screens, both ANSI and ASCII.
* VERIFIX terminates if user drops carrier.
* Windows and DESQview aware. Will give time slices back to
multitasker while waiting for keypress.
* Utility to trim the verifix log files to keep them to a managable
size
* Hitting ESCape key terminates the verification process.
* License key concept. Gives you a 45 day evaluation
period.
* Free software updates available electronically.
* 24 hour support BBS.
INSTALLATION
The following files are included in the .ZIP:
DOOR1.BAT Sample Bat File.
VERIFIX.EXE Executable File.
VERIFIX.DOC This File.
VERIFIX.HIS History file showing changes in ALL versions
VCONFIG.EXE EDITOR used to create the .CFG file.
VCONFIG.HLP The Help file for VCONFIG.
VFXBULL.EXE Utility to generate the hello or bulletin scrn.
ORDER.FRM Order form to be printed.
README.1ST Important info not in this .DOC file.
BLDNBS.EXE Generates a VERIFIED.NBS file.
DISPLAY.ZIP All the display files zipped up.
MK-CODES.EXE xxx.NBS utility.
CVT4-401.EXE Converts your .cfg file to version 4.01 style
215.NBS A sample .nbs file
TRIMVFX.EXE Utility to trim verifix log files
WHATSNEW.401 Changes for this version
Installation is simple, if you follow these directions. Keep in
mind that this is a "quick" setup. Later on in the document, each
field in VCONFIG is explained. It is assumed that the Wildcat!
BBS is up and running, and you are familiar with its operation.
Backup
1. Before installation BACKUP your system. Sophisticated
Software will not be responsible for any loss of data.
────────────────────────────────────────────────────────────────────────────
VERIFIX Call Back Verifier Manual Page -5-
Copyright (c) 1990-1992 Sophisticated Software All Rights Reserved
────────────────────────────────────────────────────────────────────────────
UnZipping
2. Place all the files from the diskette into the sub directory
that you will be running the door from. i.e.
D:\WC30\DOOR\VERIFIX
Create VERIFIX.CFG via VCONFIG.EXE
3. Create the VERIFIX.CFG file using the included editor
VCONFIG. When using VCONFIG and you aren't sure about a field,
simply press the F1 key. It is context sensitive, which means
whatever field you are in, it will give you help for THAT field.
Pressing the F10 key at each menu commits the data to memory, or
press the ESCape key to cancel out of the form.
Running BLDNBS.EXE
4. Run the BLDNBS.EXE file in the VERIFIX subdirectory. This
will search your ALLUSERS.DAT file and extract the phone numbers
for the level specified on the command line. Example: if you have
5 security levels you should run bldnbs 4 times, once for each
security level, EXCEPT the new user security level. Typing BLDNBS
FULLUSER or BLDNBS SYSOP will read through your allusers.dat file
and extract the phone numbers for that level.
Create Batch File
5. Create a DOOR1.BAT, or what ever the door number is you plan
on using, in the node home directory. Use an ASCII text editor
like Brief editor, or PC Magazine's TED. It should look like
this:
ECHO OFF
cd \wc30\door\verifix
VERIFIX
VFXBULL D:\WC30\BULL\BULL1.BBS
TRIMVFX 5
The above batch file will work if you have Wildcat! setup to run
in SWAP modeSWAP mode.
ECHO OFF
cd \wc30\door\verifix
VERIFIX
VFXBULL D:\WC30\BULL\BULL1.BBS
TRIMVFX 5
cd \wc30
cat.bat
The above batch file will work if you are NOT shelling to run
doors. Notice the VFXBULL line. Inserting the line as show will
run the program vfxbull.exe and produce a bulletin in the
directory d:\wc30\bull and create a file called bull1.bbs. Delete
this line if you do not wish to create a bulletin.
────────────────────────────────────────────────────────────────────────────
VERIFIX Call Back Verifier Manual Page -6-
Copyright (c) 1990-1992 Sophisticated Software All Rights Reserved
────────────────────────────────────────────────────────────────────────────
Creating Control File XXX.NBS
6. This next step MUST be performed! This is the second control
file VERIFIX uses. (The other control file is the verifix.cfg
file) Create a file with the name being your local area code
number with a .NBS extension. My local area code is 215 so the
file I would create would be 215.NBS. If more than 1 area code is
local to you, use the area code number that YOU have where you
live. Example, if I live in Los Angeles and I have the 123, 456,
and 789 area codes local to me, but the area code where I live is
456, then I would create a 456.NBS file. In this file you will
insert all of the LOCAL area codes and prefixes in your area.
Remember, that is all the LOCAL area codes and prefixes. By
local, I DO NOT mean whether it is a toll call or not, instead if
you have to dial a 1 and the area code, then it is NOT local to
you. Example, if you live in area code 456, and you dial the
number 234-0912, that is local, but, if you must dial
1-456-234-0912, that is long distance. Also 1-234-0912 is
considered long distance to verifix. Either case could be a free
call depending on your phone company and your area.
In some states where you must dial the area code ALL the time,
then insert all your FREE prefixes in the .nbs file. Later on,
when running VCONFIG, there is a special field for the "dial all
numbers with area codes" switch.
There are 4 formats to the .NBS file. One format is
AREACODE-PREFIX, another is AREACODE-ALL, another format is
!AREACODE-PREFIX, and the last format is !AREACODE-ALL. If you
live in an area that has more than one local area code then just
insert that area code and prefix. You must use a text editor and
each line is its own entry. Look at the following example, it
shows all 4 formats:
/* call all numbers in 215 area code */
215-ALL
/* numbers in New Jersey local to me */
609-345
609-856
609-192
/* selectively call all prefixes in 717 area code (long distance) */
!717-ALL
/* selectively call 958 prefix in 201 area code (long distance) */
!201-958
Notice I have /* comments */ in the above example. That is fine
providing you do NOT put any numbers or exclamation points in your
comments. Also take note that I have 2 local area codes in my
area, 215 and 609, in this example. Notice the 215-ALL. The
keyword ALL means that I am calling every prefix in the 215 area
code. In other words, the 1 or area code will not be dialed when
the prefixes in the 215 area code are dialed.
The next "group" of numbers are local to me (i.e. 609-345, 609-
856, and 609-192), but they are not in my local area code of 215.
I do not have to dial 1-609 to dial these 3 prefixes. Again, the
1-areacode will not be dialed when calling into these 3 prefixes.
────────────────────────────────────────────────────────────────────────────
VERIFIX Call Back Verifier Manual Page -7-
Copyright (c) 1990-1992 Sophisticated Software All Rights Reserved
────────────────────────────────────────────────────────────────────────────
The next part shows !717-ALL. Notice the ! in front of the area
code. This means that I will be dialing every prefix in the 717
area code, BUT they are NOT LOCAL TO ME. So, the 1-717 would be
dialed when any prefix in the 717 area code is dialed. On the
last line, I have !201-958, this means that 201 is also long
distance to me, I will be calling into that area, but I will only
dial the 958 prefix. Using the ! in front of an area code
selectively lets you call into a long distance area code.
If you wish to use this selective long distance calling, then you
MUST set up your verifix.cfg file in this way: Long Distance is a
Y, Dial long distance areacodes is a N, Dial long distance
prefixes is also a N. In the .NBS file, you cannot insert ranges
of numbers. They must all be individual entries. This could be a
problem if you live in a big city with say 4 local area codes,
each area code having 200 local prefixes. In order to make your
life easier, read the following section.
Running MK-CODES.EXE
Create a file called ACODES.NBS. In there, insert your ranges
in this form:
215-968~971
215-345~355
609-100~400
!717-225~350
First is the exclaimation point, then the area code, then a
dash, then the START prefix, then a tilde, then the END prefix,
then a carriage return (hit the enter key). Insert as many
entries as you wish. Also, insert all your individual entries
as show in the other example. Once you have this text file
built, run MK-CODES.EXE. This file will parse the ACODES.NBS
and create an xxx.NBS file (xxx is your area code number) with
all the ranges expanded out. So this entry:
215-968~970
produces:
215-968
215-969
215-970
in the xxx.NBS file.
7. If you intend to use the powerful feature of sending a message
to the user you must have the message utility POSTMSTR.EXE in the
path. If you intend on letting the verified user download your
allfiles file then you must have DSZ.com in the path.
Postmaster can be obtained from Mustang's The CatHouse BBS as
POSTMSTR.ZIP. DSZ.com can be obtained from any fine bbs.
CREATING A BULLETIN OR HELLO SCREEN
Verifix can now create a bulletin or hello screen. The file it
────────────────────────────────────────────────────────────────────────────
VERIFIX Call Back Verifier Manual Page -8-
Copyright (c) 1990-1992 Sophisticated Software All Rights Reserved
────────────────────────────────────────────────────────────────────────────
runs to create such screens is called VFXBULL.EXE. You simply
pass the complete path and filename to be created to the program.
Here are some examples:
VFXBULL D:\WC30\DISP\HELLO9.BBS
This will create a hello screen called hello9.bbs in the
d:\wc30\disp subdirectory.
VFXBULL D:\WC30\BULL\BULL33.BBS
This will create a file called bull33.bbs in the d:\wc30\bull
subdirectory.
If you wish to create this bulletin or hello screen, place the
extra line in your batch file that calls verifix. Look at this
example batch file for door1.bat
cd\wc30\doors\vfx
verifix
vfxbull c:\wc3\bull\bull8.bbs
RUNNING THE LOG TRIMMER TRIMVFX.EXE
There is a log trimming utility packaged with the .zip file, its
name is TRIMVFX.EXE. The purpose of this file is to trim all of
verifix's log files, keeping them to within a managable size. The
syntax is TRIMVFX 4 where 4 is the number of days you wish to
save. TRIMVFX will trim all the VALIDYES.xxx, VALIDNO.xxx and the
LOGDIST.LOG files. You can run this utility as an event or put it
as the last in your batch file that calls verifix.
Example: You run a multinode system, and have VALIDYES.001,
VALIDYES.002, and VALIDYES.003 files in your verifix subdirectory.
Typing TRIMVFX 10 will save the last 10 days in all three files.
VCONFIG FIELDS EXPLAINED
In this section, all the fields found in vconfig.exe will be
explained.
GENERAL INFORMATION
-------------------
First Name:
Enter your (the SysOp's) first name.
Last Name:
Enter your (the SysOp's) last name.
BBS Name:
Enter your (the SysOp's) BBS name.
Path to Node Home:
Enter the NODE HOME path of Wildcat! This is the same directory
ACTIVITY.001 (the log file) gets written.
Example: D:\WC30
────────────────────────────────────────────────────────────────────────────
VERIFIX Call Back Verifier Manual Page -9-
Copyright (c) 1990-1992 Sophisticated Software All Rights Reserved
────────────────────────────────────────────────────────────────────────────
Path to the VERIFIX log file:
This field permits you to specify the path you wish VERIFIX to
write its log files: VALIDYES.xxx and VALIDNO.xxx where xxx is the
node number. If you want the logs written to the root directory,
then JUST enter the drive and a :, i.e. D: VERIFIX appends the \
to it already!!
Example: C:\WC30\DOORS\VERIFIX
Example: E:\LOGS
Example: D:
Tone / Pulse:
Does your phone use Tone or a Pulse when dialing? Valid choices
are T (tone) or P (pulse).
Area Code:
Enter your (the SysOp's) LOCAL primary area code. (This is the
area code which you are dialing from)
Example: if you live in Philadelphia you would enter 215.
CTS / RTS Handshaking:
If your modem uses hardware handshaking, insert a Y. Otherwise
insert a N for XON/XOFF (software) handshaking. If you are
unsure, insert a N.
Call Back Attempts:
Insert the number of times you want VERIFIX to attempt to call
back the "waiting" pre-verified user. For instance, if the user
doesn't answer the call back, VERIFIX will time out, then try
again. It will attempt to call the user the number of times you
insert in this field. A good number to start with is 5.
Modem Initialization String:
This is the PRE-INIT string sent to the modem after VERIFIX drops
carrier on the user, right before call back. Example: placing an
M1L1 in this field turns on the modem speaker, on high volume. DO
NOT enter the AT letters as the first command. VERIFIX will
automatically enter these for you.
Free Form Phone Number Entry:
This field should ALWAYS be a N if using VERIFIX from within the
United States. All other countries have a different format for
their phone numbers, thus they would insert a Y in this field.
Prefix Added to Local Calls:
Enter the prefix you want VERIFIX to dial before it dials ANY
other local numbers. This is useful in an office environment when
you need to dial a 9, to get out. The , is for a modem pause. If
you don't use this option just leave this field blank.
Example: 9,
────────────────────────────────────────────────────────────────────────────
VERIFIX Call Back Verifier Manual Page -10-
Copyright (c) 1990-1992 Sophisticated Software All Rights Reserved
────────────────────────────────────────────────────────────────────────────
Prefix Added to Long Distance Calls:
Enter the prefix you want VERIFIX to dial before it dials ANY long
distance numbers. This is useful in an office environment when
you need to dial a 9, to get out. The , is for modem pause. You
can also use this if you wish to use an AT&T long distance line.
Then you would put 10288 in this field. If you don't use this
option leave it blank.
Example: 9,
Example: 9,10288
Suffix Added to Long Distance Phone Calls:
Enter the suffix you want VERIFIX to append to the end of the
phone number to be dialed. Some calling cards require you to
enter your ID AFTER you dial the number. Example: if the long
distance calling number was 1-123-456-7890 after appending the
suffix field (,,1029384756) it would look like this:
1-123-456-7890,,1029384756. If you are not using this field,
leave it blank.
Example: ,,1049283471
SECURITY LEVEL INFORMATION
--------------------------
New User Security Level:
Enter the new user or the pre-verified security level here. You
can enter multiple levels. Make sure that you have the
corresponding levels specified in Wildcat!
Example: NEWUSER
Example: WC1
Verified User Security Level:
Enter the security level verified users get on your BBS. You can
enter multiple levels, just make sure that you have a
corresponding verified level defined in Wildcat.
Example: VERIFIED
Example: WC5
Example: FULLUSER
Example: VIS-SYSOP
Minutes to Add to a Newly VERIFIED User:
After the user has been verified, how many additional minutes do
you wish to give? These added minutes WILL ONLY BE FOR THAT DAY.
Valid choices are from 0 to 99.
Re-verify User:
If a user becomes verified, the user will not normally be able to
────────────────────────────────────────────────────────────────────────────
VERIFIX Call Back Verifier Manual Page -11-
Copyright (c) 1990-1992 Sophisticated Software All Rights Reserved
────────────────────────────────────────────────────────────────────────────
run through the verification door again. However, if you specify
a Y for that level, VERIFIX WILL let the user run through the door
again, even though their records reflect a verified status.
Evidently some sysops want users to become re-verified.
CALLING INFORMATION
-------------------
Is Long Distance Allowed?:
Do you want VERIFIX to call back other users that are long
distance? Valid choices are Y (yes) or N (no). IF YOU INTEND ON
USING THE SELECTIVE LONG DISTANCE CALL BACK (a ! before the
areacode in the xxx.nbs field), THIS FIELD MUST BE A Y.
Is Long Distance Area Code Dialing Allowed?:
If long distance is chosen, do you want VERIFIX to call back users
who have long distance area codes? This lets you selectively call
back users who only have a long distance area code. Some SysOps
may have Reach Out America plans or something similar that only
applies to out of state calling. Valid choices are Y (yes) or N
(no). IF SELECTIVE LONG DISTANCE CALL BACK IS USED (a ! before
the areacode in the xxx.nbs field), THIS FIELD MUST BE A N.
Is Long Distance Prefix Dialing Allowed?:
If long distance is chosen, do you want VERIFIX to call back users
who have long distance prefixes? This lets you selectively call
back long distance but ONLY within the same area codes listed in
your .nbs file. Valid choices are Y (yes) or N (no). IF
SELECTIVE LONG DISTANCE CALL BACK IS USED (a ! before the
areacode in the xxx.nbs field), THIS FIELD MUST BE A N.
Should your local Area Code be added to long distance
prefixes?:
In some states, like Washington, you need to dial the area code
even though it is only a long distance prefix within the same area
code. For instance, my area code is 215. If 215-123-4567 is a
long distance prefix to me, I just dial 123-4567. If you select Y
in this field then 215-123-4567 will be dialed in this example.
Most SysOps should insert a N in this field.
Should VERIFIX add a 1 to call long distance prefixes?:
If the user you are calling back is a long distance prefix, BUT he
is in your same local area code, should a 1 be added to the
number? Valid choices are Y (yes) or N (no).
Example: Inserting a Y in this field makes 234-9539 into 1-
234-9539.
Drop Carrier on Verified User IF user is LOCAL:
If the user is a "LOCAL" call, do you want VERIFIX to drop carrier
(hang up) AFTER they have been verified? Valid choices are Y or
N.
Example: Inserting a Y here will hang up the user after
verification. The user must call back to access the bbs.
────────────────────────────────────────────────────────────────────────────
VERIFIX Call Back Verifier Manual Page -12-
Copyright (c) 1990-1992 Sophisticated Software All Rights Reserved
────────────────────────────────────────────────────────────────────────────
Inserting a N here does NOT hang up the user, wildcat would then
restart.
Drop Carrier on Verified User IF user is Long Distance:
If the user is a "LONG DISTANCE" call (if you are allowing long
distance calls), do you want VERIFIX to drop carrier (hang up)
AFTER verification? Valid choices are Y or N
Example: Inserting a Y here will hang up the user after
verification. The user must call back to access the bbs.
Inserting a N here does NOT hang up the user, wildcat would then
restart. YOU PAY THE TOLL CHARGES!
If Long Distance is 'N', auto upgrade the user without callback?:
Insert a Y or N in this field. This is handy if you do NOT call
long distance but you want to upgrade the caller to a verified
status anyway.
Example: You are NOT calling long distance at all. Someone logs
onto your bbs as a new user, they happen to be calling from across
the country. They proceed to use verifix to get verified, you
have this autoupgrade field set to a Y. The user is asked all
information just like usual, BUT instead of verifix dropping
carrier on the user to call him back, verifix upgrades them right
there without a call back. The user is then taken back to the bbs
but with an upgraded status.
The reasoning behind this is that if the user attempted to become
verified, they are probably honest, and not trying to "crack" the
board. Insert a N in this field to turn off this field.
How many seconds before VERIFIX times-out (per attempt) when
making a long distance call?:
Insert the number of seconds VERIFIX waits, per attempt, for the
user to pick up the phone via modem. For example, if you are
using tone dialing, a good starting number is 60 seconds. That is
approximately 5 rings. When 60 seconds expires VERIFIX will
time-out, then try to call the user back again. A good reason to
raise this number is when you have a pulse dial telephone line.
Naturally it takes longer to dial the numbers. Valid choices are
numbers up to 99 seconds.
How many seconds before VERIFIX times out (per attempt) when
making a local call?:
Insert the number of seconds VERIFIX waits, per attempt, for the
user to pick up the phone via modem. If you are using tone
dialing, a good starting number here is 30. That is approximately
5 rings. When 30 seconds expires VERIFIX will times-out, then try
to call the user back again. A good reason to raise this number
is when you have a pulse dial telephone line. Naturally it takes
longer to dial the numbers. Valid choices are numbers up to 99
seconds.
LONG DISTANCE TIMES INFORMATION
-------------------------------
────────────────────────────────────────────────────────────────────────────
VERIFIX Call Back Verifier Manual Page -13-
Copyright (c) 1990-1992 Sophisticated Software All Rights Reserved
────────────────────────────────────────────────────────────────────────────
Long Distance Start Time:
Insert (in MILITARY time format) when you want VERIFIX to start
calling back long distance. The rates are cheaper in PA from
17:00 till 06:00 the next day. 60% off starts at 22:00 hours.
NOTE: If you want to turn off long distance for that start/stop
period then enter 99:99 for Start Time and 99:99 for Stop Time.
This is handy if you only wish to call long distance on weekends.
Monday through Friday insert 99:99 99:99 then insert the
start/stop times for Friday -> Saturday, and Saturday Sunday
period. The default is 22:00 as you can see, which is 10 PM.
Long Distance Stop Time:
Insert (in MILITARY time format) when you want VERIFIX to stop
calling back long distance.
Example: Regular rates take affect at 06:00 in Pennsylvania
NOTE: If you want to turn off long distance for that start/stop
period then enter 99:99 for Start Time and 99:99 for Stop Time.
This is handy if you only wish to call long distance on weekends.
Monday through Friday insert 99:99 -> 99:99 then insert the
start/stop times for Friday -> Saturday and Saturday -> Sunday
period.
Default is 06:00
NO VERIFY TIMES INFORMATION
---------------------------
No Verification Start Time:
Insert (in MILITARY time format) when you want VERIFIX to start
the period when NO verification will take place.
Example: 02:00 means start the NO verify time at 2 a.m.
The no verification fields override EVERY time field. This means
that if you have long distance calling turned on during the no
verify time period, VERIFIX will NOT dial out at all!
No Verification Stop Time:
Insert the amount of hours from the start time you do not VERIFIX
to verify users. Example: you insert a 4 in this field, and there
is a 02:00 in the start no verify time. This means that from
02:00 till 06:00 verification is disabled. Note: The no
verification fields override EVERY time field. This means that if
you have long distance calling turned on during the no verify time
period, VERIFIX will NOT dial out at all!
MISCELLANOUS INFORMATION
------------------------
Download ALLFILES file Long Distance:
Some SysOps generate, as an event, an all files file listing.
This is usually a text file of all the files and descriptions
zipped up for the user to download and view off line. Do you want
the user to be able to download your allfiles.zip file or whatever
────────────────────────────────────────────────────────────────────────────
VERIFIX Call Back Verifier Manual Page -14-
Copyright (c) 1990-1992 Sophisticated Software All Rights Reserved
────────────────────────────────────────────────────────────────────────────
the name is if they are calling long distance. If you choose Yes
then you pay long distance charges. MAKE SURE DSZ.EXE or DSZ.COM
IS IN YOUR PATH!
Download ALLFILES file Locally:
Some SysOps generate as an event an all files file listing. This
is usually a text file of all the files and descriptions zipped up
for the user to download and view off line. Do you want the user
to be able to download your allfiles.zip or whatever the file name
is, if they are calling locally. MAKE SURE DSZ.EXE or DSZ.COM IS
IN YOUR PATH!
Path and filename of your ALLFILES file:
If you choose Y in one of the 2 above fields, then you need to
tell VERIFIX the complete drive, path, and name of the file the
user can download. If the name of your file is ALLFILES.ZIP then
you must say something like E:\WC\INFILES\ALLFILES.ZIP Specify the
drive, path AND file name with NO trailing backslash. MAKE SURE
DSZ.EXE or DSZ.COM IS IN YOUR PATH!
SoundSound:
This field gives you the opportunity to write your OWN musical
alarm. This alarm will sound when the user connects, becomes
verified, or fails verification. Leave this field blank if NO
alarm is to be heard.
Standard ANSI music codes are used. Here is a list of all the
music commands supported by VERIFIX:
REMEMBER: Press the F2 key to hear the tune in the field!
A. . G -> Musical notes from A to G. If you want to add an
occidental (sharp) then add an S after that note. Here is an
example: AS or FS would produce sharp notes. A note may also be
followed by a "." which will extend that note by one half of its
existing value. For instance if you are playing 1/4 notes then
adding a "." to say F. would extend it to a 3/4 note JUST for that
note.
Ln -> Specifies the default length of the notes following. "n"
must be either a 1, 2, 4, 8, or 16 where L1 is a whole note, L2 is
a half note, etc. The default is L4 or quarter note.
On -> Specifies the octave of the notes to follow. Note this is
an "O" not the zero character! Valid octaves are 0 through 7. The
default octave is 3.
Pn -> Specifies that no sound is to be played for that interval.
This is called a "rest". Valid rests are 1, 2, 4, 8, or 16.
example: P1 would rest for 1 whole note.
An example of sound would be:
Notes to sound on Connect: O6L16BCBCBCBCBC
Notes to sound on VERIFY: O2L8FFFL4AFA
Notes to sound on Fail: O1L2ASF
────────────────────────────────────────────────────────────────────────────
VERIFIX Call Back Verifier Manual Page -15-
Copyright (c) 1990-1992 Sophisticated Software All Rights Reserved
────────────────────────────────────────────────────────────────────────────
Message written to SysOp upon verification of user:
Selecting Y for this field enables VERIFIX to write the SysOp a
message regarding the new verification. MAKE SURE YOU HAVE
the utility POSTMSTR.EXE IN THE PATH for this option to work. A
default message is sent, SysOp can not modify it.
Message written to User upon successful verification:
Selecting Y for this field enables VERIFIX to write the newly
verified user a message. MAKE SURE YOU HAVE the message utility
POSTMSTR.EXE IN THE PATH for this option to work. The SysOp CAN
have a custom message sent, the file name to create this custom
message is called MESS.USR. If MESS.USR is found in the VERIFIX
subdirectory then postmaster will send this message to the
verified user. If MESS.USR is not found then a default message
will be sent to the user.
Name of the sysop to send messages to:
If you have verifix configured to send the sysop messages based on
the user's verification, place the name of the sysop here. For
example, I go by "sysop" on my bbs so I'd put SYSOP in this field.
If you use your name as sysop on your bbs, then insert your name
here. Example: John Smith
QUIT VCONFIG
------------
To quit the editor VCONFIG, highlight this option, and press enter.
CREATING OPTIONAL FILES
VERIFIX will use certain files if they are found. They are not
needed, but highly recommended.
AREACODE.BAD -- Create an ASCII text file called AREACODE.BAD and
insert the area codes you do NOT want to call no matter what!
Example:
201
516
911
555
000
976
Make sure that every number is on a different line. Do NOT use
ranges of numbers like 201-210. This will not work.
PREFIX.BAD
PREFIX.BAD -- Create an ASCII text file called PREFIX.BAD and
insert the prefixes you do NOT want to call no matter what!
Example:
555
────────────────────────────────────────────────────────────────────────────
VERIFIX Call Back Verifier Manual Page -16-
Copyright (c) 1990-1992 Sophisticated Software All Rights Reserved
────────────────────────────────────────────────────────────────────────────
911
000
976
Make sure that every number is on a different line.
The AREACODE.BAD and PREFIX.BAD files are for your protection.
This way the caller will not have YOUR system call the police or
directory assistance! It is not necessary to create AREACODE.BAD
and PREFIX.BAD files; but if found, VERIFIX will use them. Make
sure that the *.BAD files you create are in the VERIFIX directory.
MESS.USR
MESS.USR -- Create this text file using an ASCII editor. When
verifix verifies a user, and you selected the option to send the
newly verified user a message in VCONFIG, this message is sent
rather than the default congratulations message. This file must
be in your verifix subdirectory.
Files VERIFIX creates at runtime
VERIFIED.NBS -- This file is created by verifix and when you ran
the BLDNBS.EXE utility. Every time verifix is run, if the user
becomes verified, it will append the voice and/or data phone
numbers to this file.
Example: If the user originally tells Wildcat! that his phone
number is 215-123-4567, but he/she is verified at 215- 765-4321 it
will write BOTH numbers into the VERIFIED.NBS file, and also write
this information to the log files for your records.
VERIFIX.DAT -- Verifix creates this file after the user was
verified. VFXBULL.EXE uses the info found in the .dat file to
create the bulletin.
VERIFIX.ERR -- If there was an error at run time, it will be
written to this file. Check this file periodically to see if
there as been any errors. It is OK to delete this file whenever
you wish.
LONGDIST.LOG -- If you have long distance call back enabled,
VERIFIX will keep a log of all the long distance callers it
connects with. In this log will be the location of the call, and
how many minutes and/or seconds the user was on-line. The timer
starts when you call the user back, and a carrier is found. The
timer stops when VERIFIX hangs up the user.
DISPLAY FILES
In version 4.0 of verifix, there are sample display screens
included in the .zip file. You can edit each screen to your
liking. Also notice that verifix uses the SAME format that
wildcat uses for the display screens. You only need one file for
both mono and color displays, using a .BBS file extension. The
.BBS display files use the @ color codes. Modify these display
files with a program called Wildraw.
────────────────────────────────────────────────────────────────────────────
VERIFIX Call Back Verifier Manual Page -17-
Copyright (c) 1990-1992 Sophisticated Software All Rights Reserved
────────────────────────────────────────────────────────────────────────────
Here is a description of each display file:
WELCOME.BBS -- First displayed when VERIFIX calls the user back.
It should say something like "Welcome back to Sophisticated
Software BBS". What is your password.
BYE.BBS -- Good-bye screen.
VERIFIED.BBS -- Displayed when the user has successfully been
verified.
NOTVALID.BBS -- Displayed when user fails verification.
NOTNEW.BBS -- Displayed when an already verified AND upgraded user
accesses VERIFIX.
BENCALED.BBS -- Displayed when a verified but NOT upgraded user
accesses VERIFIX.
NOLOC-PF.BBS -- Displayed when the user enters a prefix that is
out of YOUR dialing range.
NOLOC-AC.BBS -- Displayed when the user enters an area code that
is out of YOUR dialing range.
CALLUSER.BBS -- Displayed to the user after they enter
a phone number. This screen has instructions on what to do during
call back. Like for them to type in ATA or ATS0=1 to pick up the
phone.
TOOLATE.BBS -- Displayed when the user tries to become verified in
a time that matches your NON callback time. Example, if a no call
back time is from 3:00 am to 6:00 am and the user enters VERIFIX
at 4:00 am, this screen will be displayed.
LDOFF.BBS -- Displayed when the user is calling long distance, and
the current time is not in the range of your long distance call
back time.
DOWNLOAD.BBS -- Displayed when the user was successfully upgraded,
and you have selected Y in VCONFIG in the "download allfiles file"
option.
AUTOUP.BBS -- Displayed if the user was just auto upgraded without
callback.
Variables VERIFIX uses if found in display files
Verifix reads its own @var@ variables that are imbedded into any
display file. Here is a list of variables that verifix support:
CLS -- Clears the screen
NAME -- Users first and last name
SEC_LEVEL -- The users current security level
LOCATION -- The users location
PASSWORD -- The users password
────────────────────────────────────────────────────────────────────────────
VERIFIX Call Back Verifier Manual Page -18-
Copyright (c) 1990-1992 Sophisticated Software All Rights Reserved
────────────────────────────────────────────────────────────────────────────
PHONE -- The users phone number
TRIES -- The amount of attempts to call back the user for
that session
BELL -- Sounds the speaker bell
VERSION -- The current version of VERIFIX
TIME -- The current time of day as set by your computer
Example: In one of your display files insert @CLS@ to clear the
screen or @NAME@ to display the users full name.
CARRIER LOSS
VERIFIX will sense loss of carrier and will shut itself down and
return back to the BBS software on its own. You can run a
Watchdog program if it makes you feel better, but it is not
needed. VERIFIX will also write to the activity that carrier loss
was detected.
MISCELLANEOUS
VERIFIX knows if it is running under DESQview or Windows. If
either one is detected, it will give back time slices to the
multitasker at all "press a key" prompts, and delays. Also, if
DESQview is found, VERIFIX will write all screen displays to the
DESQview video buffer instead of directly to the screen. This
will prevent screen bleed through into other DESQview windows.
VERIFIX also interprets modem return codes, therefore during call
back, if VERIFIX gets a busy signal it will end that call and try
again.
Log Files
VERIFIX writes its own activity logs in the directory that you
specified in the configuration file; it also writes to the
Wildcat! activity log file. The name of the file VERIFIX writes
to are VALIDYES.xxx and VALIDNO.xxx. The xxx are for node
numbers. If you run a single line version, the .001 will replace
the .xxx. If you are running a multi-node version, then the log
file extension can be as high as .250. I run 1 modem line node
and 1 local node, therefore my log files will look like this:
VALIDYES.001
Validated user list on node 1
VALIDYES.002
Validated user list on node 2
VALIDNO.001
Failed validation user list on node 1
VALIDNO.002
Failed validation user list on node 2
VALIDYES.XXX
This file is written if a new user successfully completes the
verification process. It writes the following to the log file:
────────────────────────────────────────────────────────────────────────────
VERIFIX Call Back Verifier Manual Page -19-
Copyright (c) 1990-1992 Sophisticated Software All Rights Reserved
────────────────────────────────────────────────────────────────────────────
1. Users Name.
2. Time verified.
3. Date verified.
4. If the number dialed is different from WILDCAT! database
number.
5. If there was an incoming call during verification.
VALIDNO.XXX
This file is written if a new user fails the verification process
for any of the following reasons:
1. Security level too high or too low. (not new user)
2. No answer after 3 tries.
3. Wrong Password.
4. Dropped Carrier.
5. Unacceptable area code and prefix entered (as defined by
the SysOp).
6. The call was long distance and you are not verifying long
distance callers.
7. Calling in a "NO VERIFY" time period.
VERIFIX also writes the above information to the Wildcat!
activity.### log file. If you run a single node, then VERIFIX
will write to the activity.001 file. It will track the user, and
append his/her actions to the activity.001 file. If you run a
multi-node version of Wildcat!, VERIFIX will write to activity.002
if node 2 is used. It is important to have SET WCNODEID=2 in your
cat.bat file. This tells VERIFIX what log to write to.
LOCAL MODE
VERIFIX has the ability to run in local mode. All carrier
checking is turned off, and there is no actual callback. This is
particularly helpful when you want to check your custom screens
before going "on line". To start VERIFIX in local mode with color
screens displayed, simply type VERIFIX -L at the DOS prompt. If
you want to display mono screens, then start VERIFIX in the local
mode by typing VERIFIX -L -M. Another way to test VERIFIX locally
is to start Wildcat! locally, then execute the door that runs
VERIFIX. This time it will read your DOOR.SYS and USERINFO.DAT
files. Your name and password will appear at the bottom of the
screen. When finished, and you entered the correct password,
VERIFIX will even upgrade you to the level specified in the .cfg
file.
One quick note; when running VERIFIX from the DOS prompt, there
are no userinfo.dat or door.sys files present. VERIFIX
substitutes the name and password field as Master SysOp and
VFX_TEST.
SPECIAL APPLICATIONS
Having read this document, you now know the operation of VERIFIX,
────────────────────────────────────────────────────────────────────────────
VERIFIX Call Back Verifier Manual Page -20-
Copyright (c) 1990-1992 Sophisticated Software All Rights Reserved
────────────────────────────────────────────────────────────────────────────
and all the files VERIFIX uses and manipulates. If you have a
special application, like verifying users and not upgrading them,
or verifying EVERY user on EVERY call, this is how it can be done.
Start VCONFIG. In the field New User Level #1 type SYSOP and in
the Upgrade Level #1 also type SYSOP. Now when the SYSOP level
runs through VERIFIX and passes validation, VERIFIX will upgrade
the SYSOP level to SYSOP level, or no upgrade will take place.
This is because the user is already at the SYSOP level!
MULTI NODE USAGE
Environment Variables
VERIFIX can successfully be run in a multi-node configuration.
Here are the steps needed:
1. Make sure that you have the SET WCNODEID= environment variable
set in your catx.bat file. This is extremely important!
2. Set a VERIFIX environment variable in each of your node's
cat.bat file. This tells VERIFIX to override the default settings
found in the VERIFIX.CFG file. If no SET variable is found,
VERIFIX will use what is in the .cfg file.
Here is a list of environment variables that VERIFIX reads if
present:
SET VFXLD=
SET VFXTP=
SET VFXLDAC=
SET VFXLDPF=
SET VFXDROPLOCAL=
SET VFXDROPLD=
SET VFXLOGPATH=
SET VFXMDMINIT=
SET VFXFREEFORM=
SET VFXAUTOUP=
SET VFXRELATIVE=
SET VFXCTSRTS=
SET WCMDM=
SET WCBASEID=
SET WCIRQID=
Some examples of setting the variables:
SET VFXLD=Y or SET VFXLD=N. This overrides the long distance yes
no configuration file directive.
SET VFXTP=T or SET VFXTP=P. This tells verifix to dial with a
tone or pulse.
SET VFXLDAC=Y or SET VFXLDAC=N. This tells verifix if it is ok to
dial area codes on that node.
────────────────────────────────────────────────────────────────────────────
VERIFIX Call Back Verifier Manual Page -21-
Copyright (c) 1990-1992 Sophisticated Software All Rights Reserved
────────────────────────────────────────────────────────────────────────────
SET VFXLDPF=Y or SET VFXLDPF=N. This tells verifix if it is ok to
dial long distance prefixes on that node.
SET VFXDROPLOCAL=Y or SET VFXDROPLOCAL=N. This tells verifix to
drop or not to drop carrier with a local call back connection.
SET VFXDROPLD=Y or SET VFXDROPLD=N. This tells verifix to drop or
not to drop carrier when your call back was long distance
connection. If N was chosen, then the caller will stay on-line.
Remember it is long distance so you pay the phone bill.
SET VFXLOGPATH=D:\WC3\MYLOGS or whatever drive and directory you
wish to store the VALIDYES.xxx and the VALIDNO.xxx log files.
SET VFXMDMINIT=M0V1E1X5 or whatever you wish to send as an
initialization string to that modem on that node.
SET VFXFREEFORM=Y or SET VFXFREEFORM=N toggles free form number
entry on that node.
SET VFXAUTOUP=Y or SET VFXAUTOUP=N toggles the auto upgrade switch
SET VFXRELATIVE=Y or SETVFXRELATIVE=N toggles the call back
relative switch for that node.
SET VFXCTSRTS=Y or SET VFXCTSRTS=N toggles the modem cts/rts
handshaking for that node.
SET WCMDM you set this environment variable if your modem settings
are different for each node. VERIFIX will read this file and open
the port specified using the IRQ and BASE id found in your .MDM
file.
SET WCBASEID if this variable is found, and no WCMDM variable is
found, VERIFIX will open up the comm port at this hexidecimal
address.
SET WCIRQID if this variable is found, and no WCMDM variable is
found, VERIFIX will open up the comm port using this custom IRQ.
Log Files
If using a multi-node version of Wildcat!, VERIFIX will write to
its logfile.node and to the activity.node files. For example, if
there is a caller on node 18, then the files ACTIVITY.018 and
VALIDYES.018 or VALIDNO.018 will be written to.
UPGRADING USERS
VERIFIX does NOT write to the Wildcat! databases, per se, it
changes information in the userinfo.dat file. When Wildcat! is
started up after returning from the door, it will re-read the info
found in this file and then write to its database. What can be
more safe than having Wildcat! write to its own database!
QUESTIONS AND ANSWERS
────────────────────────────────────────────────────────────────────────────
VERIFIX Call Back Verifier Manual Page -22-
Copyright (c) 1990-1992 Sophisticated Software All Rights Reserved
────────────────────────────────────────────────────────────────────────────
Q. I realize that verifix has an areacode.bad file and a
prefix.bad file, but I don't want verifix to call the police at
say 234-9432, how do I set it up so this won't happen?
A. In the verified.nbs file, just type on a line 234-9432;POLICE
this will tell verifix that the number was already called, so it
won't re-call it.
Q. Sometimes my users pick up the phone and say HELLO when called
back. How do I stop this?
A. You should modify the calluser.bbs screen and give the user
more information about what the call back procedure is. All the
display screens are included for EXAMPLE ONLY. You can modify the
screens to say whatever you like!
Q. I only want to call long distance into 3 area codes, how do I
tell verifix to do that?
A. In your xxx.nbs file (xxx is your area code) you should put a
! in front of the areacode-prefix number. Then in vconfig, tell
it long distance Y but long distance areacode and long distance
prefix calling both must be NO.
Example, say you want to call into 717, 456, and 678 areacodes.
In your xxx.nbs file you will put:
!717-ALL
!456-ALL
!678-ALL
Q. Sometimes I want test verifix from remote and don't want to
have to keep going into the verified.nbs file to delete the number
that was verified. How can I reverify myself with out doing all
this?
A. In the security level form, flag that level as Y in the field
REVERIFY
Q. I don't want to call long distance, BUT I really don't feel
like going into WCPRO to upgrade all the long distance users
manually to a verified level, can verifix do that for me?
A. Of course. Go into VCONFIG, get into the Long Distance Info
form. You probably already have Long Distance Calling set to a N.
Go to the field that says Auto Upgrade Long Distance Callers, and
make sure that field says Y. Now when a long distance caller logs
in, and runs through verifix, they will be automatically upgraded
to the verified level you specified WITHOUT call back.
USER SUPPORT
If you have any questions, problems or suggestions we would like
to hear from you. The latest version of VERIFIX can be had from
the following BBS:
Sophisticated Software BBS
(215) 968-4998
24 Hours
────────────────────────────────────────────────────────────────────────────
VERIFIX Call Back Verifier Manual Page -23-
Copyright (c) 1990-1992 Sophisticated Software All Rights Reserved
────────────────────────────────────────────────────────────────────────────
Fidonet 1:273/215
*HST* V.42bis
Thanks for your continued support!
Ed Blazejewski.
────────────────────────────────────────────────────────────────────────────
VERIFIX Call Back Verifier Manual Page -24-